Secure single sign on and conditional access for client applications

ABSTRACT

Methods and systems for implementing single sign on (SSO) and/or conditional access for client applications are described herein. The system may comprise an identity provider gateway, and the system may authenticate a user of the client application using the identity provider gateway. In some aspects, a secure communication tunnel may be established between the client application and the identity provider gateway, and the secure communication tunnel may use, for example, a client certificate. The identity provider gateway may grant or deny the client application access to one or more resources based on information associated with the client certificate.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. patent applicationSer. No. 15/919,935, filed Sep. Mar. 13, 2018 and entitled “SECURESINGLE SIGN ON AND CONDITIONAL ACCESS FOR CLIENT APPLICATIONS,” which isa continuation of U.S. patent application Ser. No. 15/716,871 (now U.S.Pat. No. 9,948,612), filed Sep. 27, 2017 and entitled “SECURE SINGLESIGN ON AND CONDITIONAL ACCESS FOR CLIENT APPLICATIONS.” The priorapplications are incorporated herein by reference in their entirety.

FIELD

Aspects described herein generally relate to computer networking anddata security. More specifically, aspects described herein relate togranting client devices access to one or more resources using singlesign on and/or conditional access mechanisms.

BACKGROUND

Increasingly, software applications (e.g., enterprise applications) maybe consumed using devices that might not be corporate issued devices,such as bring your own device (BYOD) devices. End users may desire aconsumer-like user experience for their enterprise applications. Forexample, users may desire the ability to perform single sign on (SSO) toenterprise applications. At the same time, IT departments may desireenterprise data to be securely consumed by authorized users, onauthorized endpoints, and using authorized applications. They may alsodesire to leverage technologies, such as machine learning, to recognizeanomalous behaviors and limit access to enterprise data usingconditional access mechanisms.

SSO and conditional access may be challenging for certain platforms,such as mobile device platforms. For example, mobile platforms (e.g.iOS, Android, Windows 10, etc.) may be strong on application sandboxing,which may prevent traditional solutions for SSO that are used on desktopcomputers (e.g., shared system key-chain or shared authenticationcookies). Mobile endpoints may be BYOD devices and may havenon-enterprise applications installed by, for example, the end user.There is a need to control which applications have access to the SSOfunctionality. There is also a need to consider factors that affectconditional access decisions.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

A secure communication tunnel may be established between an applicationrunning on a mobile device and an identity provider gateway device. Theidentity provider gateway device may receive, from the applicationrunning on the mobile device, and via the secure communication tunnel,an authentication request comprising a client certificate. The identityprovider gateway device may extract, from the client certificate, adevice identifier associated with the mobile device. The identityprovider gateway device may transmit, to a device management server, arequest to determine whether the mobile device is compliant withsecurity policies. The request to determine whether the mobile device iscompliant with security policies may comprise the device identifierassociated with the mobile device. In response to transmitting therequest to determine whether the mobile device is compliant withsecurity policies, the identity provider gateway device may receive,from the device management server, an indication of whether the mobiledevice is compliant with security policies. The identity providergateway device may determine, based on the indication of whether themobile device is compliant with security policies, whether to grant theapplication running on the mobile device access to a service associatedwith the application running on the mobile device.

In some aspects, establishing the secure communication tunnel maycomprise detecting a request, by the application running on the mobiledevice, to access the identity provider gateway device. A tunnelingapplication may intercept the request to access the identity providergateway device. The tunneling application may establish, using theclient certificate, the secure communication tunnel between theapplication running on the mobile device and the identity providergateway device. Establishing the secure communication tunnel may beperformed in response to a request, from a service provider of theservice, to redirect the authentication request to the identity providergateway device. The secure communication tunnel may comprise a virtualprivate network (VPN) tunnel.

In some aspects, after determining to grant access to the service, theidentity provider gateway device may retrieve cached authentication dataassociated with the mobile device. The identity provider gateway devicemay generate, using the cached authentication data, an authenticationtoken. The identity provider gateway device may transmit, to the mobiledevice, the authentication token. The authentication token may be usedby the mobile device to access the service associated with theapplication running on the mobile device.

In some aspects, the identity provider gateway device may determine thatauthentication data associated with the mobile device is not cached atthe identity provider gateway device. In response to determining thatthe authentication data is not cached at the identity provider gatewaydevice, the identity provider gateway device may transmit, to the mobiledevice, a request for the authentication data from an identity providerdevice. The identity provider gateway device may receive, from themobile device, and via the identity provider device, the authenticationdata associated with the mobile device. The identity provider gatewaydevice may cache the authentication data associated with the mobiledevice. After a predetermined amount of time, the identity providergateway device may remove the cached authentication data associated withthe mobile device.

In some aspects, the identity provider gateway device may retrieve thecached authentication data associated with the mobile device. Theidentity provider gateway device may generate, using the cachedauthentication data, an authentication token. The identity providergateway device may transmit, to the mobile device, the authenticationtoken.

In some aspects, after determining to grant access to the service, theidentity provider gateway device may extract, from the clientcertificate, a user identifier associated with a user of the mobiledevice. The identity provider gateway device may generate, using theuser identifier, an authentication token. The identity provider gatewaydevice may transmit, to the mobile device, the authentication token.

In some aspects, after extracting the user identifier, the identityprovider gateway device may transmit, to a directory service, a requestfor additional data associated with the user of the mobile device. Theidentity provider gateway device may receive, from the directoryservice, the additional data associated with the user of the mobiledevice. Generating the authentication token may comprise generating theauthentication token using the user identifier and the additional dataassociated with the user received from the directory service.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative remote-access system architecture thatmay be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3 depicts an illustrative virtualized (hypervisor) systemarchitecture that may be used in accordance with one or moreillustrative aspects described herein.

FIG. 4 depicts an illustrative cloud-based system architecture that maybe used in accordance with one or more illustrative aspects describedherein.

FIG. 5 depicts an illustrative enterprise mobility management system.

FIG. 6 depicts another illustrative enterprise mobility managementsystem.

FIG. 7 depicts an illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein.

FIGS. 8A-B depict an illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein.

FIG. 9 depicts another illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein.

FIG. 10 depicts yet another illustrative system and method for singlesign on and/or conditional access for client applications in accordancewith one or more illustrative aspects described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (also known as, remote desktop), virtualized, and/orcloud-based environments, among others. FIG. 1 illustrates one exampleof a system architecture and data processing device that may be used toimplement one or more illustrative aspects described herein in astandalone and/or networked environment. Various network nodes 103, 105,107, and 109 may be interconnected via a wide area network (WAN) 101,such as the Internet. Other networks may also or alternatively be used,including private intranets, corporate networks, LANs, metropolitan areanetworks (MAN) wireless networks, personal networks (PAN), and the like.Network 101 is for illustration purposes and may be replaced with feweror additional computer networks. A local area network (LAN) may have oneor more of any known LAN topology and may use one or more of a varietyof different protocols, such as Ethernet. Devices 103, 105, 107, 109 andother devices (not shown) may be connected to one or more of thenetworks via twisted pair wires, coaxial cable, fiber optics, radiowaves or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects describe herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the network 101 (e.g., theInternet), via direct or indirect connection, or via some other network.Users may interact with the data server 103 using remote computers 107,109, e.g., using a web browser to connect to the data server 103 via oneor more externally exposed web sites hosted by web server 105. Clientcomputers 107, 109 may be used in concert with data server 103 to accessdata stored therein, or may be used for other purposes. For example,from client device 107 a user may access web server 105 using anInternet browser, as is known in the art, or by executing a softwareapplication that communicates with web server 105 and/or data server 103over a computer network (such as the Internet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include random access memory (RAM) 113, read onlymemory (ROM) 115, network interface 117, input/output interfaces 119(e.g., keyboard, mouse, display, printer, etc.), and memory 121.Input/output (I/O) 119 may include a variety of interface units anddrives for reading, writing, displaying, and/or printing data or files.Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or might not be used in conjunctionwith aspects described herein. The control logic may also be referred toherein as the data server software 125. Functionality of the data serversoftware may refer to operations or decisions made automatically basedon rules coded into the control logic, made manually by a user providinginput into the system, and/or a combination of automatic processingbased on user input (e.g., queries, data updates, etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 129 and a seconddatabase 131. In some embodiments, the first database may include thesecond database (e.g., as a separate table, report, etc.). That is, theinformation can be stored in a single database, or separated intodifferent logical, virtual, or physical databases, depending on systemdesign. Devices 105, 107, 109 may have similar or different architectureas described with respect to device 103. Those of skill in the art willappreciate that the functionality of data processing device 103 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to)HyperText Markup Language (HTML) or Extensible Markup Language (XML).The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, one or more aspects described hereinmay be implemented in a remote-access environment. FIG. 2 depicts anexample system architecture including a generic computing device 201 inan illustrative computing environment 200 that may be used according toone or more illustrative aspects described herein. Generic computingdevice 201 may be used as a server 206 a in a single-server ormulti-server desktop virtualization system (e.g., a remote access orcloud system) configured to provide virtual machines for client accessdevices. The generic computing device 201 may have a processor 203 forcontrolling overall operation of the server and its associatedcomponents, including RAM 205, ROM 207, I/O module 209, and memory 215.

I/O module 209 may include a mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of generic computing device 201 may provide input, and may alsoinclude one or more of a speaker for providing audio output and a videodisplay device for providing textual, audiovisual, and/or graphicaloutput. Software may be stored within memory 215 and/or other storage toprovide instructions to processor 203 for configuring generic computingdevice 201 into a special purpose computing device in order to performvarious functions as described herein. For example, memory 215 may storesoftware used by the computing device 201, such as an operating system217, application programs 219, and an associated database 221.

Computing device 201 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 240 (alsoreferred to as client devices). The terminals 240 may be personalcomputers, mobile devices, laptop computers, tablets, or servers thatinclude many or all of the elements described above with respect to thegeneric computing device 103 or 201. The network connections depicted inFIG. 2 include a local area network (LAN) 225 and a wide area network(WAN) 229, but may also include other networks. When used in a LANnetworking environment, computing device 201 may be connected to the LAN225 through a network interface or adapter 223. When used in a WANnetworking environment, computing device 201 may include a modem 227 orother wide area network interface for establishing communications overthe WAN 229, such as computer network 230 (e.g., the Internet). It willbe appreciated that the network connections shown are illustrative andother means of establishing a communications link between the computersmay be used. Computing device 201 and/or terminals 240 may also bemobile terminals (e.g., mobile phones, smartphones, personal digitalassistants (PDAs), notebooks, etc.) including various other components,such as a battery, speaker, and antennas (not shown).

Aspects described herein may also be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of other computing systems, environments,and/or configurations that may be suitable for use with aspectsdescribed herein include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network personal computers (PCs), minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

As shown in FIG. 2, one or more client devices 240 may be incommunication with one or more servers 206 a-206 n (generally referredto herein as “server(s) 206”). In one embodiment, the computingenvironment 200 may include a network appliance installed between theserver(s) 206 and client machine(s) 240. The network appliance maymanage client/server connections, and in some cases can load balanceclient connections amongst a plurality of backend servers 206.

The client machine(s) 240 may in some embodiments be referred to as asingle client machine 240 or a single group of client machines 240,while server(s) 206 may be referred to as a single server 206 or asingle group of servers 206. In one embodiment a single client machine240 communicates with more than one server 206, while in anotherembodiment a single server 206 communicates with more than one clientmachine 240. In yet another embodiment, a single client machine 240communicates with a single server 206.

A client machine 240 can, in some embodiments, be referenced by any oneof the following non-exhaustive terms: client machine(s); client(s);client computer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); or endpointnode(s). The server 206, in some embodiments, may be referenced by anyone of the following non-exhaustive terms: server(s), local machine;remote machine; server farm(s), or host computing device(s).

In one embodiment, the client machine 240 may be a virtual machine. Thevirtual machine may be any virtual machine, while in some embodimentsthe virtual machine may be any virtual machine managed by a Type 1 orType 2 hypervisor, for example, a hypervisor developed by CitrixSystems, IBM, VMware, or any other hypervisor. In some aspects, thevirtual machine may be managed by a hypervisor, while in aspects thevirtual machine may be managed by a hypervisor executing on a server 206or a hypervisor executing on a client 240.

Some embodiments include a client device 240 that displays applicationoutput generated by an application remotely executing on a server 206 orother remotely located machine. In these embodiments, the client device240 may execute a virtual machine receiver program or application todisplay the output in an application window, a browser, or other outputwindow. In one example, the application is a desktop, while in otherexamples the application is an application that generates or presents adesktop. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications, as used herein, areprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded.

The server 206, in some embodiments, uses a remote presentation protocolor other program to send data to a thin-client or remote-displayapplication executing on the client to present display output generatedby an application executing on the server 206. The thin-client orremote-display protocol can be any one of the following non-exhaustivelist of protocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

A remote computing environment may include more than one server 206a-206 n such that the servers 206 a-206 n are logically grouped togetherinto a server farm 206, for example, in a cloud computing environment.The server farm 206 may include servers 206 that are geographicallydispersed while and logically grouped together, or servers 206 that arelocated proximate to each other while logically grouped together.Geographically dispersed servers 206 a-206 n within a server farm 206can, in some embodiments, communicate using a WAN (wide), MAN(metropolitan), or LAN (local), where different geographic regions canbe characterized as: different continents; different regions of acontinent; different countries; different states; different cities;different campuses; different rooms; or any combination of the precedinggeographical locations. In some embodiments the server farm 206 may beadministered as a single entity, while in other embodiments the serverfarm 206 can include multiple server farms.

In some embodiments, a server farm may include servers 206 that executea substantially similar type of operating system platform (e.g.,WINDOWS, UNIX, LINUX, iOS, ANDROID, SYMBIAN, etc.) In other embodiments,server farm 206 may include a first group of one or more servers thatexecute a first type of operating system platform, and a second group ofone or more servers that execute a second type of operating systemplatform.

Server 206 may be configured as any type of server, as needed, e.g., afile server, an application server, a web server, a proxy server, anappliance, a network appliance, a gateway, an application gateway, agateway server, a virtualization server, a deployment server, a SecureSockets Layer (SSL) VPN server, a firewall, a web server, an applicationserver or as a master application server, a server executing an activedirectory, or a server executing an application acceleration programthat provides firewall functionality, application functionality, or loadbalancing functionality. Other server types may also be used.

Some embodiments include a first server 206 a that receives requestsfrom a client machine 240, forwards the request to a second server 206b, and responds to the request generated by the client machine 240 witha response from the second server 206 b. First server 206 a may acquirean enumeration of applications available to the client machine 240 andwell as address information associated with an application server 206hosting an application identified within the enumeration ofapplications. First server 206 a can then present a response to theclient's request using a web interface, and communicate directly withthe client 240 to provide the client 240 with access to an identifiedapplication. One or more clients 240 and/or one or more servers 206 maytransmit data over network 230, e.g., network 101.

FIG. 2 shows a high-level architecture of an illustrative desktopvirtualization system. As shown, the desktop virtualization system maybe single-server or multi-server system, or cloud system, including atleast one virtualization server 206 configured to provide virtualdesktops and/or virtual applications to one or more client accessdevices 240. As used herein, a desktop refers to a graphical environmentor space in which one or more applications may be hosted and/orexecuted. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications may include programsthat execute after an instance of an operating system (and, optionally,also the desktop) has been loaded. Each instance of the operating systemmay be physical (e.g., one operating system per device) or virtual(e.g., many instances of an OS running on a single device). Eachapplication may be executed on a local device, or executed on a remotelylocated device (e.g., remoted).

With further reference to FIG. 3, a computer device 301 may beconfigured as a virtualization server in a virtualization environment,for example, a single-server, multi-server, or cloud-computingenvironment. Virtualization server 301 illustrated in FIG. 3 can bedeployed as and/or implemented by one or more embodiments of the server206 illustrated in FIG. 2 or by other known computing devices. Includedin virtualization server 301 is a hardware layer that can include one ormore physical disks 304, one or more physical devices 306, one or morephysical processors 308 and one or more physical memories 316. In someembodiments, firmware 312 can be stored within a memory element in thephysical memory 316 and can be executed by one or more of the physicalprocessors 308. Virtualization server 301 may further include anoperating system 314 that may be stored in a memory element in thephysical memory 316 and executed by one or more of the physicalprocessors 308. Still further, a hypervisor 302 may be stored in amemory element in the physical memory 316 and can be executed by one ormore of the physical processors 308.

Executing on one or more of the physical processors 308 may be one ormore virtual machines 332A-C (generally 332). Each virtual machine 332may have a virtual disk 326A-C and a virtual processor 328A-C. In someembodiments, a first virtual machine 332A may execute, using a virtualprocessor 328A, a control program 320 that includes a tools stack 324.Control program 320 may be referred to as a control virtual machine,Dom0, Domain 0, or other virtual machine used for system administrationand/or control. In some embodiments, one or more virtual machines 332B-Ccan execute, using a virtual processor 328B-C, a guest operating system330A-B.

Virtualization server 301 may include a hardware layer 310 with one ormore pieces of hardware that communicate with the virtualization server301. In some embodiments, the hardware layer 310 can include one or morephysical disks 304, one or more physical devices 306, one or morephysical processors 308, and one or more memory 316. Physical components304, 306, 308, and 316 may include, for example, any of the componentsdescribed above. Physical devices 306 may include, for example, anetwork interface card, a video card, a keyboard, a mouse, an inputdevice, a monitor, a display device, speakers, an optical drive, astorage device, a universal serial bus connection, a printer, a scanner,a network element (e.g., router, firewall, network address translator,load balancer, virtual private network (VPN) gateway, Dynamic HostConfiguration Protocol (DHCP) router, etc.), or any device connected toor communicating with virtualization server 301. Physical memory 316 inthe hardware layer 310 may include any type of memory. Physical memory316 may store data, and in some embodiments may store one or moreprograms, or set of executable instructions. FIG. 3 illustrates anembodiment where firmware 312 is stored within the physical memory 316of virtualization server 301. Programs or executable instructions storedin the physical memory 316 can be executed by the one or more processors308 of virtualization server 301.

Virtualization server 301 may also include a hypervisor 302. In someembodiments, hypervisor 302 may be a program executed by processors 308on virtualization server 301 to create and manage any number of virtualmachines 332. Hypervisor 302 may be referred to as a virtual machinemonitor, or platform virtualization software. In some embodiments,hypervisor 302 can be any combination of executable instructions andhardware that monitors virtual machines executing on a computingmachine. Hypervisor 302 may be Type 2 hypervisor, where the hypervisorthat executes within an operating system 314 executing on thevirtualization server 301. Virtual machines then execute at a levelabove the hypervisor. In some embodiments, the Type 2 hypervisorexecutes within the context of a user's operating system such that theType 2 hypervisor interacts with the user's operating system. In otherembodiments, one or more virtualization servers 301 in a virtualizationenvironment may instead include a Type 1 hypervisor (not shown). A Type1 hypervisor may execute on the virtualization server 301 by directlyaccessing the hardware and resources within the hardware layer 310. Thatis, while a Type 2 hypervisor 302 accesses system resources through ahost operating system 314, as shown, a Type 1 hypervisor may directlyaccess all system resources without the host operating system 314. AType 1 hypervisor may execute directly on one or more physicalprocessors 308 of virtualization server 301, and may include programdata stored in the physical memory 316.

Hypervisor 302, in some embodiments, can provide virtual resources tooperating systems 330 or control programs 320 executing on virtualmachines 332 in any manner that simulates the operating systems 330 orcontrol programs 320 having direct access to system resources. Systemresources can include, but are not limited to, physical devices 306,physical disks 304, physical processors 308, physical memory 316 and anyother component included in virtualization server 301 hardware layer310. Hypervisor 302 may be used to emulate virtual hardware, partitionphysical hardware, virtualize physical hardware, and/or execute virtualmachines that provide access to computing environments. In still otherembodiments, hypervisor 302 controls processor scheduling and memorypartitioning for a virtual machine 332 executing on virtualizationserver 301. Hypervisor 302 may include those manufactured by VMWare,Inc., of Palo Alto, Calif.; the XEN hypervisor, an open source productwhose development is overseen by the open source Xen.org community;HyperV, VirtualServer or virtual PC hypervisors provided by Microsoft,or others. In some embodiments, virtualization server 301 executes ahypervisor 302 that creates a virtual machine platform on which guestoperating systems may execute. In these embodiments, the virtualizationserver 301 may be referred to as a host server. An example of such avirtualization server is the XEN SERVER provided by Citrix Systems,Inc., of Fort Lauderdale, Fla.

Hypervisor 302 may create one or more virtual machines 332B-C (generally332) in which guest operating systems 330 execute. In some embodiments,hypervisor 302 may load a virtual machine image to create a virtualmachine 332. In other embodiments, the hypervisor 302 may executes aguest operating system 330 within virtual machine 332. In still otherembodiments, virtual machine 332 may execute guest operating system 330.

In addition to creating virtual machines 332, hypervisor 302 may controlthe execution of at least one virtual machine 332. In other embodiments,hypervisor 302 may presents at least one virtual machine 332 with anabstraction of at least one hardware resource provided by thevirtualization server 301 (e.g., any hardware resource available withinthe hardware layer 310). In other embodiments, hypervisor 302 maycontrol the manner in which virtual machines 332 access physicalprocessors 308 available in virtualization server 301. Controllingaccess to physical processors 308 may include determining whether avirtual machine 332 should have access to a processor 308, and howphysical processor capabilities are presented to the virtual machine332.

As shown in FIG. 3, virtualization server 301 may host or execute one ormore virtual machines 332. A virtual machine 332 is a set of executableinstructions that, when executed by a processor 308, imitate theoperation of a physical computer such that the virtual machine 332 canexecute programs and processes much like a physical computing device.While FIG. 3 illustrates an embodiment where a virtualization server 301hosts three virtual machines 332, in other embodiments virtualizationserver 301 can host any number of virtual machines 332. Hypervisor 302,in some embodiments, provides each virtual machine 332 with a uniquevirtual view of the physical hardware, memory, processor and othersystem resources available to that virtual machine 332. In someembodiments, the unique virtual view can be based on one or more ofvirtual machine permissions, application of a policy engine to one ormore virtual machine identifiers, a user accessing a virtual machine,the applications executing on a virtual machine, networks accessed by avirtual machine, or any other desired criteria. For instance, hypervisor302 may create one or more unsecure virtual machines 332 and one or moresecure virtual machines 332. Unsecure virtual machines 332 may beprevented from accessing resources, hardware, memory locations, andprograms that secure virtual machines 332 may be permitted to access. Inother embodiments, hypervisor 302 may provide each virtual machine 332with a substantially similar virtual view of the physical hardware,memory, processor and other system resources available to the virtualmachines 332.

Each virtual machine 332 may include a virtual disk 326A-C (generally326) and a virtual processor 328A-C (generally 328.) The virtual disk326, in some embodiments, is a virtualized view of one or more physicaldisks 304 of the virtualization server 301, or a portion of one or morephysical disks 304 of the virtualization server 301. The virtualizedview of the physical disks 304 can be generated, provided and managed bythe hypervisor 302. In some embodiments, hypervisor 302 provides eachvirtual machine 332 with a unique view of the physical disks 304. Thus,in these embodiments, the particular virtual disk 326 included in eachvirtual machine 332 can be unique when compared with the other virtualdisks 326.

A virtual processor 328 can be a virtualized view of one or morephysical processors 308 of the virtualization server 301. In someembodiments, the virtualized view of the physical processors 308 can begenerated, provided and managed by hypervisor 302. In some embodiments,virtual processor 328 has substantially all of the same characteristicsof at least one physical processor 308. In other embodiments, virtualprocessor 308 provides a modified view of physical processors 308 suchthat at least some of the characteristics of the virtual processor 328are different than the characteristics of the corresponding physicalprocessor 308.

With further reference to FIG. 4, some aspects described herein may beimplemented in a cloud-based environment. FIG. 4 illustrates an exampleof a cloud computing environment (or cloud system) 400. As seen in FIG.4, client computers 411-414 may communicate with a cloud managementserver 410 to access the computing resources (e.g., host servers 403,storage resources 404, and network resources 405) of the cloud system.

Management server 410 may be implemented on one or more physicalservers. The management server 410 may run, for example, CLOUDSTACK, orOPENSTACK, among others. Management server 410 may manage variouscomputing resources, including cloud hardware and software resources,for example, host computers 403, data storage devices 404, andnetworking devices 405. The cloud hardware and software resources mayinclude private and/or public components. For example, a cloud may beconfigured as a private cloud to be used by one or more particularcustomers or client computers 411-414 and/or over a private network. Inother embodiments, public clouds or hybrid public-private clouds may beused by other customers over an open or hybrid networks.

Management server 410 may be configured to provide user interfacesthrough which cloud operators and cloud customers may interact with thecloud system. For example, the management server 410 may provide a setof application programming interfaces (APIs) and/or one or more cloudoperator console applications (e.g., web-based on standaloneapplications) with user interfaces to allow cloud operators to managethe cloud resources, configure the virtualization layer, manage customeraccounts, and perform other cloud administration tasks. The managementserver 410 also may include a set of APIs and/or one or more customerconsole applications with user interfaces configured to receive cloudcomputing requests from end users via client computers 411-414, forexample, requests to create, modify, or destroy virtual machines withinthe cloud. Client computers 411-414 may connect to management server 410via the Internet or other communication network, and may request accessto one or more of the computing resources managed by management server410. In response to client requests, the management server 410 mayinclude a resource manager configured to select and provision physicalresources in the hardware layer of the cloud system based on the clientrequests. For example, the management server 410 and additionalcomponents of the cloud system may be configured to provision, create,and manage virtual machines and their operating environments (e.g.,hypervisors, storage resources, services offered by the networkelements, etc.) for customers at client computers 411-414, over anetwork (e.g., the Internet), providing customers with computationalresources, data storage services, networking capabilities, and computerplatform and application support. Cloud systems also may be configuredto provide various specific services, including security systems,development environments, user interfaces, and the like.

Certain clients 411-414 may be related, for example, different clientcomputers creating virtual machines on behalf of the same end user, ordifferent users affiliated with the same company or organization. Inother examples, certain clients 411-414 may be unrelated, such as usersaffiliated with different companies or organizations. For unrelatedclients, information on the virtual machines or storage of any one usermay be hidden from other users.

Referring now to the physical hardware layer of a cloud computingenvironment, availability zones 401-402 (or zones) may refer to acollocated set of physical computing resources. Zones may begeographically separated from other zones in the overall cloud ofcomputing resources. For example, zone 401 may be a first clouddatacenter located in California, and zone 402 may be a second clouddatacenter located in Florida. Management sever 410 may be located atone of the availability zones, or at a separate location. Each zone mayinclude an internal network that interfaces with devices that areoutside of the zone, such as the management server 410, through agateway. End users of the cloud (e.g., clients 411-414) might or mightnot be aware of the distinctions between zones. For example, an end usermay request the creation of a virtual machine having a specified amountof memory, processing power, and network capabilities. The managementserver 410 may respond to the user's request and may allocate theresources to create the virtual machine without the user knowing whetherthe virtual machine was created using resources from zone 401 or zone402. In other examples, the cloud system may allow end users to requestthat virtual machines (or other cloud resources) are allocated in aspecific zone or on specific resources 403-405 within a zone.

In this example, each zone 401-402 may include an arrangement of variousphysical hardware components (or computing resources) 403-405, forexample, physical hosting resources (or processing resources), physicalnetwork resources, physical storage resources, switches, and additionalhardware resources that may be used to provide cloud computing servicesto customers. The physical hosting resources in a cloud zone 401-402 mayinclude one or more computer servers 403, such as the virtualizationservers 301 described above, which may be configured to create and hostvirtual machine instances. The physical network resources in a cloudzone 401 or 402 may include one or more network elements 405 (e.g.,network service providers) comprising hardware and/or softwareconfigured to provide a network service to cloud customers, such asfirewalls, network address translators, load balancers, virtual privatenetwork (VPN) gateways, Dynamic Host Configuration Protocol (DHCP)routers, and the like. The storage resources in the cloud zone 401-402may include storage disks (e.g., solid state drives (SSDs), magnetichard disks, etc.) and other storage devices.

The example cloud computing environment shown in FIG. 4 also may includea virtualization layer (e.g., as shown in FIGS. 1-3) with additionalhardware and/or software resources configured to create and managevirtual machines and provide other services to customers using thephysical resources in the cloud. The virtualization layer may includehypervisors, as described above in FIG. 3, along with other componentsto provide network virtualizations, storage virtualizations, etc. Thevirtualization layer may be as a separate layer from the physicalresource layer, or may share some or all of the same hardware and/orsoftware resources with the physical resource layer. For example, thevirtualization layer may include a hypervisor installed in each of thevirtualization servers 403 with the physical computing resources. Knowncloud systems may alternatively be used, e.g., WINDOWS AZURE (MicrosoftCorporation of Redmond Washington), AMAZON EC2 (Amazon.com Inc. ofSeattle, Wash.), IBM BLUE CLOUD (IBM Corporation of Armonk, N.Y.), orothers.

Enterprise Mobility Management Architecture

FIG. 5 represents an enterprise mobility technical architecture 500 foruse in a BYOD environment. The architecture enables a user of a mobiledevice 502 to both access enterprise or personal resources from a mobiledevice 502 and use the mobile device 502 for personal use. The user mayaccess such enterprise resources 504 or enterprise services 508 using amobile device 502 that is purchased by the user or a mobile device 502that is provided by the enterprise to user. The user may utilize themobile device 502 for business use only or for business and personaluse. The mobile device may run an iOS operating system, and Androidoperating system, or the like. The enterprise may choose to implementpolicies to manage the mobile device 504. The policies may be implantedthrough a firewall or gateway in such a way that the mobile device maybe identified, secured or security verified, and provided selective orfull access to the enterprise resources. The policies may be mobiledevice management policies, mobile application management policies,mobile data management policies, or some combination of mobile device,application, and data management policies. A mobile device 504 that ismanaged through the application of mobile device management policies maybe referred to as an enrolled device.

In some embodiments, the operating system of the mobile device may beseparated into a managed partition 510 and an unmanaged partition 512.The managed partition 510 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the mobile device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is not accessibleby unmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The secure applicationsmay be secure native applications 514, secure remote applications 522executed by a secure application launcher 518, virtualizationapplications 526 executed by a secure application launcher 518, and thelike. The secure native applications 514 may be wrapped by a secureapplication wrapper 520. The secure application wrapper 520 may includeintegrated policies that are executed on the mobile device 502 when thesecure native application is executed on the device. The secureapplication wrapper 520 may include meta-data that points the securenative application 514 running on the mobile device 502 to the resourceshosted at the enterprise that the secure native application 514 mayrequire to complete the task requested upon execution of the securenative application 514. The secure remote applications 522 executed by asecure application launcher 518 may be executed within the secureapplication launcher application 518. The virtualization applications526 executed by a secure application launcher 518 may utilize resourceson the mobile device 502, at the enterprise resources 504, and the like.The resources used on the mobile device 502 by the virtualizationapplications 526 executed by a secure application launcher 518 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 504, and the like. The resources used at theenterprise resources 504 by the virtualization applications 526 executedby a secure application launcher 518 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a graphical user interface (GUI) and communicate them toa server application where the server application may use the userinteraction data as an input to the application operating on the server.In this arrangement, an enterprise may elect to maintain the applicationon the server side as well as data, files, etc. associated with theapplication. While an enterprise may elect to “mobilize” someapplications in accordance with the principles herein by securing themfor deployment on the mobile device, this arrangement may also beelected for certain applications. For example, while some applicationsmay be secured for use on the mobile device, others might not beprepared or appropriate for deployment on the mobile device so theenterprise may elect to provide the mobile user access to the unpreparedapplications through virtualization techniques. As another example, theenterprise may have large complex applications with large and complexdata sets (e.g., material resource planning applications) where it wouldbe very difficult, or otherwise undesirable, to customize theapplication for the mobile device so the enterprise may elect to provideaccess to the application through virtualization techniques. As yetanother example, the enterprise may have an application that maintainshighly secured data (e.g., human resources data, customer data,engineering data) that may be deemed by the enterprise as too sensitivefor even the secured mobile environment so the enterprise may elect touse virtualization techniques to permit mobile access to suchapplications and data. An enterprise may elect to provide both fullysecured and fully functional applications on the mobile device as wellas a virtualization application to allow access to applications that aredeemed more properly operated on the server side. In an embodiment, thevirtualization application may store some data, files, etc. on themobile phone in one of the secure storage locations. An enterprise, forexample, may elect to allow certain information to be stored on thephone while not permitting other information.

In connection with the virtualization application, as described herein,the mobile device may have a virtualization application that is designedto present GUIs and then record user interactions with the GUI. Theapplication may communicate the user interactions to the server side tobe used by the server side application as user interactions with theapplication. In response, the application on the server side maytransmit back to the mobile device a new GUI. For example, the new GUImay be a static page, a dynamic page, an animation, or the like, therebyproviding access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 528 in the managed partition 510 of the mobile device. Thedata secured in the secure data container may be accessed by the securewrapped applications 514, applications executed by a secure applicationlauncher 522, virtualization applications 526 executed by a secureapplication launcher 522, and the like. The data stored in the securedata container 528 may include files, databases, and the like. The datastored in the secure data container 528 may include data restricted to aspecific secure application 530, shared among secure applications 532,and the like. Data restricted to a secure application may include securegeneral data 534 and highly secure data 538. Secure general data may usea strong form of encryption such as Advanced Encryption Standard (AES)128-bit encryption or the like, while highly secure data 538 may use avery strong form of encryption such as AES 256-bit encryption. Datastored in the secure data container 528 may be deleted from the deviceupon receipt of a command from the device manager 524. The secureapplications may have a dual-mode option 540. The dual mode option 540may present the user with an option to operate the secured applicationin an unsecured or unmanaged mode. In an unsecured or unmanaged mode,the secure applications may access data stored in an unsecured datacontainer 542 on the unmanaged partition 512 of the mobile device 502.The data stored in an unsecured data container may be personal data 544.The data stored in an unsecured data container 542 may also be accessedby unsecured applications 548 that are running on the unmanagedpartition 512 of the mobile device 502. The data stored in an unsecureddata container 542 may remain on the mobile device 502 when the datastored in the secure data container 528 is deleted from the mobiledevice 502. An enterprise may want to delete from the mobile deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The mobile device 502 may connect to enterprise resources 504 andenterprise services 508 at an enterprise, to the public Internet 548,and the like. The mobile device may connect to enterprise resources 504and enterprise services 508 through virtual private network connections.The virtual private network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications(e.g., as illustrated by microVPNs 550), particular devices, particularsecured areas on the mobile device (e.g., as illustrated by O/S VPN552), and the like. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 554. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 558. The authentication service 558 may thengrant to the user access to multiple enterprise resources 504, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 504.

The virtual private network connections may be established and managedby an access gateway 560. The access gateway 560 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 504 to the mobile device 502. The access gatewaymay also re-route traffic from the mobile device 502 to the publicInternet 548, enabling the mobile device 502 to access publiclyavailable and unsecured applications that run on the public Internet548. The mobile device may connect to the access gateway via a transportnetwork 562. The transport network 562 may use one or more transportprotocols and may be a wired network, wireless network, cloud network,local area network, metropolitan area network, wide area network, publicnetwork, private network, and the like.

The enterprise resources 504 may include email servers, file sharingservers, SaaS applications, Web application servers, Windows applicationservers, and the like. Email servers may include Exchange servers, LotusNotes servers, and the like. File sharing servers may include ShareFileservers, and the like. SaaS applications may include Salesforce, and thelike. Windows application servers may include any application serverthat is built to provide applications that are intended to run on alocal Windows operating system, and the like. The enterprise resources504 may be premise-based resources, cloud based resources, and the like.The enterprise resources 504 may be accessed by the mobile device 502directly or through the access gateway 560. The enterprise resources 504may be accessed by the mobile device 502 via a transport network 562.The transport network 562 may be a wired network, wireless network,cloud network, local area network, metropolitan area network, wide areanetwork, public network, private network, and the like.

The enterprise services 508 may include authentication services 558,threat detection services 564, device manager services 524, file sharingservices 568, policy manager services 570, social integration services572, application controller services 574, and the like. Authenticationservices 558 may include user authentication services, deviceauthentication services, application authentication services, dataauthentication services and the like. Authentication services 558 mayuse certificates. The certificates may be stored on the mobile device502, by the enterprise resources 504, and the like. The certificatesstored on the mobile device 502 may be stored in an encrypted locationon the mobile device, the certificate may be temporarily stored on themobile device 502 for use at the time of authentication, and the like.Threat detection services 564 may include intrusion detection services,unauthorized access attempt detection services, and the like.Unauthorized access attempt detection services may include unauthorizedattempts to access devices, applications, data, and the like. Devicemanagement services 524 may include configuration, provisioning,security, support, monitoring, reporting, and decommissioning services.File sharing services 568 may include file management services, filestorage services, file collaboration services, and the like. Policymanager services 570 may include device policy manager services,application policy manager services, data policy manager services, andthe like. Social integration services 572 may include contactintegration services, collaboration services, integration with socialnetworks such as Facebook, Twitter, and Linkedln, and the like.Application controller services 574 may include management services,provisioning services, deployment services, assignment services,revocation services, wrapping services, and the like.

The enterprise mobility technical architecture 500 may include anapplication store 578. The application store 578 may include unwrappedapplications 580, pre-wrapped applications 582, and the like.Applications may be populated in the application store 578 from theapplication controller 574. The application store 578 may be accessed bythe mobile device 502 through the access gateway 560, through the publicInternet 548, or the like. The application store may be provided with anintuitive and easy to use User Interface.

A software development kit 584 may provide a user the capability tosecure applications selected by the user by wrapping the application asdescribed previously in this description. An application that has beenwrapped using the software development kit 584 may then be madeavailable to the mobile device 502 by populating it in the applicationstore 578 using the application controller 574.

The enterprise mobility technical architecture 500 may include amanagement and analytics capability. The management and analyticscapability may provide information related to how resources are used,how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 6 is another illustrative enterprise mobility management system600. Some of the components of the mobility management system 500described above with reference to FIG. 5 have been omitted for the sakeof simplicity. The architecture of the system 600 depicted in FIG. 6 issimilar in many respects to the architecture of the system 500 describedabove with reference to FIG. 5 and may include additional features notmentioned above.

In this case, the left hand side represents an enrolled mobile device602 with a client agent 604, which interacts with gateway server 606(which includes Access Gateway and application controller functionality)to access various enterprise resources 608 and services 609 such asExchange, Sharepoint, public-key infrastructure (PKI) Resources,Kerberos Resources, Certificate Issuance service, as shown on the righthand side above. Although not specifically shown, the mobile device 602may also interact with an enterprise application store (StoreFront) forthe selection and downloading of applications.

The client agent 604 acts as the UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX)/ICA displayremoting protocol. The client agent 604 also supports the installationand management of native applications on the mobile device 602, such asnative iOS or Android applications. For example, the managedapplications 610 (mail, browser, wrapped application) shown in thefigure above are all native applications that execute locally on thedevice. Client agent 604 and application management framework of thisarchitecture act to provide policy driven management capabilities andfeatures such as connectivity and SSO (single sign on) to enterpriseresources/services 608. The client agent 604 handles primary userauthentication to the enterprise, normally to Access Gateway (AG) withSSO to other gateway server components. The client agent 604 obtainspolicies from gateway server 606 to control the behavior of the managedapplications 610 on the mobile device 602.

The Secure interprocess communication (IPC) links 612 between the nativeapplications 610 and client agent 604 represent a management channel,which allows client agent to supply policies to be enforced by theapplication management framework 614 “wrapping” each application. TheIPC channel 612 also allows client agent 604 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 608. Finally the IPC channel 612 allows theapplication management framework 614 to invoke user interface functionsimplemented by client agent 604, such as online and offlineauthentication.

Communications between the client agent 604 and gateway server 606 areessentially an extension of the management channel from the applicationmanagement framework 614 wrapping each native managed application 610.The application management framework 614 requests policy informationfrom client agent 604, which in turn requests it from gateway server606. The application management framework 614 requests authentication,and client agent 604 logs into the gateway services part of gatewayserver 606 (also known as NetScaler Access Gateway). Client agent 604may also call supporting services on gateway server 606, which mayproduce input material to derive encryption keys for the local datavaults 616, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 614 “wraps” eachmanaged application 610. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 614 may “pair” with client agent 604 on first launch of anapplication 610 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 614may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 610.

The application management framework 614 may use services provided byclient agent 604 over the Secure IPC channel 612 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 616 (containers) may be also managed byappropriate interactions between the managed applications 610 and clientagent 604. Vaults 616 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 616 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 610 through Access Gateway 606. The applicationmanagement framework 614 is responsible for orchestrating the networkaccess on behalf of each application 610. Client agent 604 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 618.

The Mail and Browser managed applications 610 have special status andmay make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture supports the incorporation of various other securityfeatures. For example, gateway server 606 (including its gatewayservices) in some cases might not need to validate active directory (AD)passwords. It can be left to the discretion of an enterprise whether anAD password is used as an authentication factor for some users in somesituations. Different authentication methods may be used if a user isonline or offline (i.e., connected or not connected to a network).

Step up authentication is a feature wherein gateway server 606 mayidentify managed native applications 610 that are allowed to have accessto more sensitive data using strong authentication, and ensure thataccess to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequested from the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 616 (containers) on the mobile device 602. The vaults 616 may beencrypted so that all on-device data including files, databases, andconfigurations are protected. For on-line vaults, the keys may be storedon the server (gateway server 606), and for off-line vaults, a localcopy of the keys may be protected by a user password or biometricvalidation. When data is stored locally on the device 602 in the securecontainer 616, it is preferred that a minimum of AES 256 encryptionalgorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 610 are logged and reported to the backend. Datawiping may be supported, such as if the application 610 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase or biometric data supplied by the user (ifoffline access is required). It may be XORed with another key randomlygenerated and stored on the server side if offline access is notrequired. Key Derivation functions may operate such that keys generatedfrom the user password use KDFs (key derivation functions, notablyPassword-Based Key Derivation Function 2 (PBKDF2)) rather than creatinga cryptographic hash of it. The latter makes a key susceptible to bruteforce or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector might cause multiple copies of thesame encrypted data to yield different cipher text output, preventingboth replay and cryptanalytic attacks. This may also prevent an attackerfrom decrypting any data even with a stolen encryption key. Further,authentication then decryption may be used, wherein application data isdecrypted only after the user has authenticated within the application.Another feature may relate to sensitive data in memory, which may bekept in memory (and not in disk) only when it's needed. For example,login credentials may be wiped from memory after login, and encryptionkeys and other data inside objective-C instance variables are notstored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented, wherein after a policy-definedperiod of inactivity, a user session is terminated.

Data leakage from the application management framework 614 may beprevented in other ways. For example, when an application 610 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 620 without the use of an AD (active directory) 622 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 620 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 620. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 610 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want StoreFront to be accessed inthis manner. In this case, the client agent 604 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 606 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 610 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application may utilizesuch a certificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from theclient agent 604 may be retrieved by gateway server 606 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in gateway server606.

Gateway server 606 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 604 and the application management framework 614 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting a public-key cryptography standards (PKCS) 12 BLOB (BinaryLarge Object) into the iOS keychain in each managed application for eachperiod of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate might never be present in the iOSkeychain and might not be persisted except potentially in “online-only”data value that is strongly protected.

Mutual SSL or TLS may also be implemented to provide additional securityby requiring that a mobile device 602 is authenticated to theenterprise, and vice versa. Virtual smart cards for authentication togateway server 606 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 622, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when http (but not https) connections areproxied in VPN and MicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 610 is not running.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be service from one of several different locations in case offailure.

In some cases, managed applications 610 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 610 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is used, when an application reads a certificate for“who am I,” when an application uses the certificate to build a securesession token, and when an application uses private keys for digitalsigning of important data (e.g. transaction log) or for temporary dataencryption.

Illustrative Examples of Single Sign On and/or Conditional Access forClient Applications

Systems and methods of implementing single sign on (SSO) and/orconditional access for client applications, such as mobile applications,are described herein. One or more of the systems and methods for SSOand/or conditional access may be secure. For example, the system may beable to identify authorized users, identify authorized devices, and/oridentify authorized applications. One or more SSO and/or conditionalaccess capability described herein may be achieved securely, withoutsacrificing the ability of IT administrators to control which users,devices, and/or applications have access to the functionality. In someaspects, conditional access decisions may be made based on variousfactors, such as user identity, device identity, application identity,location of access, etc.

One or more of the systems and methods for SSO and/or conditional accessdescribed herein may be application neutral. For example, the systemsand methods described herein may handle various types of mobileapplications and/or might not require modifications to the applications(e.g., without using an SDK, without wrapping the application, etc.).One or more of the systems and methods for SSO and/or conditional accessdescribed herein may be identity provider (IDP) neutral. For example,aspects described herein may utilize and support any standards-basedIDP. One or more of the systems and methods for SSO and/or conditionalaccess described herein may be platform neutral. For example, they maysupport any popular mobile platform, such as ANDROID, iOS, WINDOWS, orany other mobile device platform.

In some aspects, one or more of the systems and methods described hereincan be used to achieve zero touch mobile SSO, such as where anauthorized user using an authorized application from an authorizeddevice can authenticate without any additional user interaction.

FIG. 7 depicts an illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein. The system may comprise aclient device 705. The client device 705 may be, for example, a mobiledevice, such as a mobile phone, a tablet, a smartwatch, a virtualreality or augmented reality headset, or any other mobile device. Theclient device 705 might not be a corporate issued or managed device andmay be, for example, a BYOD device. In some aspects, the client device705 may be device 103, device 105, device 107, or device 109 illustratedin FIG. 1, one of the terminals 240 illustrated in FIG. 2, one of theclient computers 411-414 illustrated in FIG. 4, the mobile device 502illustrated in FIG. 5, the mobile device 602 illustrated in FIG. 6, orany other client device.

The client device 705 may comprise one or more client applications 710.In some aspects, a client application may be configured to authenticatevia a particular identity provider (IDP), such as IDP 735. However, theclient application's backend service may be reconfigured to federateauthentication to an IDP gateway, such as IDP gateway 725. In federatedauthentication scenarios, a company may authenticate a user of theclient device 705 and allow access to a service provided by a serviceprovider (e.g., instead of the service provider authenticating user).

The client device 705 may comprise one or more VPN services 715. EachVPN service may comprise a per-app VPN that may be launched on demandand may be used to connect the client device 705 to the IDP gateway 725,as will be described in further detail below.

The system may comprise one or more servers 730, such as a devicemanagement server (e.g., an enterprise mobility management server in anenterprise mobility management system). The server 730 may be configuredto manage client devices, such as to install VPNs (e.g., per-app VPNs)on authorized client devices, such as the client device 705. The server730 (or another device in the system) may deliver a client certificateto the per-app VPN, and the client certificate may encode user identityinformation, device identity information (e.g., as SubjectAlternativeNames), or other user or device information. The deviceidentity information may comprise any unique string for identifying theclient device 705, and the string may be based on a configuration in thesystem. The user identity information may comprise, for example, anemail address, a username, a user principal name, or any other identityfor identifying the user of the client device 705. The server 730 (oranother device in the system) may configure the per-app VPN to useclient certificate authentication with a certificate delivered by theserver 730 (or another device in the system). In some aspects, theserver 730 (or another device in the system) may configure the per-appVPN to accept requests from authorized applications and/or to interceptrequests to the IDP gateway 725. Intercepting only certain requests maylead to more efficient use of processing resources and communicationsbandwidth by reducing the number of requests to be handled. The server730 may also be used to determine whether a client device 705 requestingaccess to resources is compliant with security policies, as will bedescribed in further detail below.

The system may comprise one or more service providers 720. The serviceprovider 720 may make one or more resources (e.g., document editingresources, customer relationship management (CRM) resources, emailservices, banking resources, etc.) available to the user of the clientdevice 705. In some aspects, application 710 may be managed, provided,and/or developed by the service provider 720 or an affiliate of theservice provider 720.

The system may comprise one or more IDP gateways 725. The IDP gateway725 may be configured to federate authentication to the original IDP 735of a back-end service (e.g., a service provided by the service provider720). The IDP gateway 725 may behave like a standards-based IDP for anyservice provider. The IDP gateway 725 may behave like a standards-basedservice provider for any standards-based IDP (e.g., a real IDP). The IDPgateway 725 may additionally or alternatively behave like a real IDP.The IDP gateway 725 may be accessed by endpoints (e.g., the clientdevice 705) either directly or via an authorized VPN tunnel.

The system may comprise one or more identity providers 735, which may bean original IDP used to authenticate the user of the client device 705.As will be described in further detail below, the identity provider 735may handle cases of access from unmanaged endpoints, desktops, and/orrogue applications.

FIGS. 8A-B depict an illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein.

In step 810, the client device (e.g., via a client application 710, suchas a mobile application) may transmit a request to access a service fromthe service provider 720. For example, a user of the client device mayselect, via an input device of the client device, such as a touchscreen, keyboard, mouse, gesture, etc., an icon for the clientapplication 710, and the client application 710 may initiatecommunications between the client device and the service provider 720.

In step 812, the service provider 720 may receive the request from theclient application 710. The service provider 710 may transmit, to theclient application 710 of the client device, a request to redirectauthentication to an identity provider (IDP) gateway 725. The request toredirect may indicate that the service provider 720 is the requestor.For example, when a mobile application authenticates, its backendservice may redirect it to the identity provider gateway 725 rather thanauthenticating directly with the service provider 720 or redirectingauthentication to the original identity provider 735. As will bedescribed in further detail below, a secure communication tunnel may beestablished between the application 710 and the identity providergateway 725 in response to the request from the service provider 720 toredirect the authentication request to the identity provider gateway725.

In step 814, the client application 710 may request to access theidentity provider gateway 725. In step 816, a tunneling application(e.g., a virtual private network (VPN) 715, such as a per-app VPNplugin) may intercept the request to access the identity providergateway 725 and may establish a secure communication tunnel (e.g., a VPNtunnel) between the client application 710 and the identity providergateway 725 using, for example, a client certificate. Establishing thesecure communication tunnel may comprise detecting (e.g., by the VPN715) a request, by the application 710 running on the client device, toaccess the identity provider gateway 725. For example, when theapplication 710 attempts to reach the identity provider gateway 725, aper-app VPN may kick in and establish a VPN tunnel using the configuredclient certificate for authentication to the VPN endpoint. The tunnelingapplication may intercept the request to access the identity providergateway 725 and/or establish the secure communication tunnel using theclient certificate. The tunneling application may encode user identityand/or device identity information in the request. In some aspects, thetunneling application may accept requests from authorized applications,but might not accept requests from unauthorized applications.Additionally or alternatively, the tunneling application may interceptrequests intended for the identity provider gateway 725, but might notaccept requests that are not intended for the identity provider gateway725.

In step 818, the identity provider gateway 725 may confirm establishmentof the secure communication tunnel between the client application 710and the identity provider gateway 725. In step 820, the VPN 715 mayreceive the confirmation and forward the confirmation to the clientapplication 710. The secure communication tunnel between the clientapplication 710 and the identity provider gateway 725 may beestablished.

In step 822, the client application 710 may transmit an authenticationrequest to the identity provider gateway 725, such as via the securecommunication tunnel. The identity provider gateway 725 may receive,from the application 710, and via the secure communication tunnel, theauthentication request, which may use a client certificate. The clientcertificate may be used to establish the tunnel itself. In otherexamples, the authentication request might not come via the securecommunication tunnel and/or might not use the client certificate.

In step 824, the identity provider gateway 725 may determine whether therequest came via a tunnel authenticated using a client certificate. If aclient certificate was not used to establish the tunnel (e.g., VPNtunnel), the identity provider gateway 725 may determine that the clientdevice is a non-managed client device. The identity provider gateway 725may determine that single sign on and conditional access are notavailable for the client request, and the identity provider gateway 725may redirect the client device to the identity provider 735 (e.g., theoriginal identity provider). This feature may handle cases of accessfrom unmanaged endpoints, desktops, and/or rogue applications. Theseaccesses might not get single sign on functionality. A newauthentication request may be constructed by the client device, and theclient device may forward the new authentication request to the identityprovider 735, instead of the identity provider gateway 725.

If, on the other hand, an authentication request came via a tunnel andused a client certificate (e.g., as determined in step 824), in step826, the identity provider gateway 725 may extract, from the clientcertificate, a device identifier for the client device (e.g., a mobiledevice) and/or a user identifier for the user. In step 828, the identityprovider gateway 725 may transmit, to the server 730 (which may comprisea device management server), a request to determine whether the client(e.g., mobile) device is compliant with security policies. The requestto determine whether the mobile device is compliant with securitypolicies may comprise the device identifier associated with the mobiledevice.

In step 830, the server 730 may return, to the identity provider gateway725, compliance information, which may indicate whether the clientdevice is compliant. For example, in response to transmitting therequest to determine whether the mobile device is compliant withsecurity policies, the identity provider gateway 725 may receive, fromthe device management server 730, an indication of whether the mobiledevice is compliant with security policies. The identity providergateway 725 may determine, based on an indication of whether the mobiledevice is compliant with security policies (e.g., which may becompliance information returned by the server 730), whether the clientdevice is compliant. The identity provider gateway 725 may determine,based on the compliance information, whether to grant the application710 running on the client device access to a service associated with theapplication 710 running on the client device and/or the service provider720. This feature may provide conditional access, such as based on adevice security profile.

In step 832, if the client device is not compliant, the identityprovider gateway 725 may deny access and/or deny authentication to theclient device. Otherwise, the identity provider gateway 725 may proceedto step 834 if, for example, the identity provider gateway 725determines that the client device is compliant and/or to otherwise grantthe client device access to services of the service provider 720.

In step 834, the identity provider gateway 725 may determine whetherunexpired cached authentication data (e.g., SAML content, such asclaims) is available for the client device. As will be described infurther detail below, the identity provider gateway 725 may cacheauthentication data associated with the client device for futureauthentication requests. The cached authentication data may have anexpiry time. If unexpired cached authentication content is available,the identity provider gateway 725 may retrieve the cached authenticationdata associated with the client device. In step 836, the identityprovider gateway 725 may generate, using the cached authentication data(e.g., SAML content, such as claims), an authentication token (e.g., aSAML token) and/or sign it. For example, the token may comprise adigitally signed assertion with the user's identifier, roots, and/orother data about the user. The identity provider gateway 725 maytransmit, to the client device (e.g., via the application 710), theauthentication token. In step 838, the authentication token may be usedby the client device to access the service associated with theapplication 710 running on the mobile device (e.g., a service providedby the service provider 720). These features may provide a single signon capability. For example, subsequent authentication requests from thesame client device within an expiry period might not require usercredential re-entry.

In some aspects, the identity provider gateway 725 may determine thatauthentication data associated with the client device is not cached atthe identity provider gateway. If cached authentication content is notavailable, the identity provider gateway 725 may redirect the clientdevice to the original identity provider 735 to authenticate and fetch atoken (e.g., SAML token). As will be described in further detail below,the identity provider gateway 725 may extract the content of the token(e.g., a SAML token), such as a set of claims, and cache the content forfuture authentication requests. In some aspects, the identity providergateway 725 may cache the content in its own memory store.

In step 840, in response to determining that authentication data is notcached at the identity provider gateway 725, the identity providergateway 725 may construct a new authentication request with the identityprovider gateway 725 as the requestor. In step 842, the identityprovider gateway 725 may transmit, to the client device (e.g., via theclient application 710), a request for the authentication data from anidentity provider 735 (e.g., an original identity provider). The requestmay comprise a request to redirect a new authentication request to theidentity provider 735. The request to redirect may indicate the identityprovider gateway 725 as the requestor.

With reference to FIG. 8B, in step 844, the client application 710 maytransmit, to the identity provider 735, a new authentication request,which may indicate the identity provider gateway 725 as the requestor.In step 846, the identity provider 735 may authenticate the user.

In step 848, the client device (e.g., via the client application 710)may request that the user of the client device enter user credentials(e.g., a passcode, a password, a PIN, etc.). Depending on theconfiguration, multiple interactions may occur in step 848. Thecredentials may be submitted to the identity provider 735, and the usermay be authenticated based on the submitted credentials.

In step 850, the identity provider 735 may transmit a request to post anidentity provider token (e.g., SAML token) to the requestor (e.g.,identity provider gateway 725). The request may include, for example,the identity provider token. The client device may receive the requestand/or the token from the identity provider 735.

In step 852, the client application 710 may transmit, to the identityprovider gateway 725, the request to post the identity provider token,with the identity provider token. The identity provider gateway 725 mayreceive, from the mobile device, the token, which may compriseauthentication data associated with the client device.

In step 854, the identity provider gateway 725 may process the identityprovider token. The identity provider gateway 725 may extract, from thetoken, the authentication data associated with the client device and maycache the authentication data. The cached authentication data maycomprise, for example, token contents (e.g., SAML token contents). Forfuture authentication requests from the client application 710 and viathe secure communication tunnel, the identity provider gateway 725 mayretrieve the cached authentication data, generate an authenticationtoken using the cached authentication data, and/or transmit theauthentication token to the client application 710 (e.g., as describedabove with reference to step 834 and step 836). After a predeterminedamount of time (e.g., an expiry time), the identity provider gatewaydevice 725 may remove the cached authentication data associated with theclient device.

In step 856, the identity provider gateway 725 may transmit a request topost the new token (e.g., SAML token) to the service provider 720. Instep 858, the client application 710 may transmit, to the serviceprovider 720, the request to post the new token. The application 710 maypresent the token (e.g., SAML token) to the service provider 720 toobtain access to resources of the service provider 720. In step 860, theservice provider 720 may process the token and grant, to the clientdevice, access to resources.

A very similar method can be used to support OpenID Connect and otherfederation standards as well. For example, an access code orauthentication code may be used instead of a token (e.g., a SAML token).An identity provider in one or more of these systems may issue tokens,which may be signed assertions similar to SAML claims.

FIG. 9 depicts another illustrative system and method for single sign onand/or conditional access for client applications in accordance with oneor more illustrative aspects described herein. In some aspects, a usermay access resources via an application store, such as the applicationstore 578 illustrated in FIG. 5, rather than directly through theservice provider 720. The application store may be provided by theidentity provider 735. The applications available to the user via theapplication store may be displayed on a display of the client device 705and/or may comprise, for example, web applications. The user may select(e.g., click on) an icon for one of the applications in the applicationstore to attempt to access resources associated with the application.

In step 910, the user may log in to an application page provided by theidentity provider 735. For example, the user may provide a username,password, passcode, or any other credentials, and the client device maytransmit the user's entered credentials to the identity provider 735. Insome aspects, the client device might not need to re-authenticate withthe identity provider gateway 725 because the client deviceauthenticated directly with the identity provider 735. The user mayselect (e.g., click on) an application icon.

In step 912, the identity provider 735 may transmit an identity providertoken (e.g., SAML token) and/or a request to post the identity providertoken to the identity provider gateway 725. The client device mayreceive the request from the identity provider 735.

In step 914, the client application 710 may transmit, to the identityprovider gateway 725, the identity provider token. The identity providergateway 725 may receive, from the client device, the token, which maycomprise authentication data associated with the client device. Thetoken may be received after authentication of the client device 710 withthe identity provider 735.

In step 916, the identity provider gateway 725 may process the identityprovider token. The identity provider gateway 725 may cache theauthentication data associated with the client device, as previouslydescribed. The cached authentication data may comprise, for example,token contents (e.g., SAML token contents). The identity providergateway 725 may retrieve the cached authentication data, generate anauthentication token using the cached authentication data, sign thetoken for the service provider 720, and/or transmit, via a securecommunication tunnel, the authentication token to the client application710. As previously described, the identity provider gateway device 725may remove the cached authentication data associated with the clientdevice after a predetermined amount of time (e.g., an expiry time).

In step 918, the identity provider gateway 725 may transmit, to theclient application 710, a request to post the new token (e.g., SAMLtoken) to the service provider 720. The client application 710 mayreceive the request from the identity provider gateway 725.

In step 920, the client application 710 may transmit, to the serviceprovider 720, the request to post the new token. The application 710 maypresent the token (e.g., SAML token) to the service provider 720 toobtain access to resources of the service provider 720. In step 922, theservice provider 720 may process the token and grant, to the clientdevice, access to resources.

In some aspects, the identity provider gateway 725 may be configured tobe and/or perform one or more authentication steps of the originalidentity provider 735. In these examples, end user authentication mayoccur at the identity provider gateway 725, rather than at the originalidentity provider 735. The client certificate, which may be presented bythe VPN 715, may be used as a factor to authenticate the user, withoutrequiring any additional input from the end user. These examples mayachieve zero touch mobile SSO.

With brief reference to step 830 illustrated in FIG. 8A, the identityprovider gateway 725 may determine whether the client device iscompliant, such as based on the compliance information returned from theserver 730. If the identity provider gateway 725 determines that theclient device is compliant and/or to otherwise grant the client deviceaccess to services of the service provider 720, the system describedherein may perform one or more steps to authenticate the user orotherwise give the user access to the services. These steps might notinvolve a redirect to the original identity provider 735. Instead, theidentity provider gateway 725 may obtain additional information from adirectory 745 (e.g., an active directory), and the additionalinformation may be used to authenticate the user and/or client device.

FIG. 10 depicts yet another illustrative system and method for singlesign on and/or conditional access for client applications in accordancewith one or more illustrative aspects described herein. After theidentity provider gateway 725 determines that the client device iscompliant (e.g., based on the compliance information received in step830) and/or otherwise determines to grant the client device access tothe service, the identity provider gateway 725, in step 1010, mayextract, from the client certificate, a user identifier associated witha user of the client (e.g., mobile) device. As previously described, theclient certificate may have been used to establish the securecommunication tunnel between the client application 710 and the identityprovider gateway 725.

In step 1012, the identity provider gateway 725 may transmit, to thedirectory 745, a request for additional data associated with the user ofthe client device. The additional user information may comprise, forexample, group membership information, whether the user has an emailaccount, the user's email address, etc. The type of informationavailable from the directory 745 may be configurable.

In step 1014, the directory 745 may transmit, to the identity providergateway 725, the additional user information requested by the identityprovider gateway 725. The identity provider gateway 725 may receive theadditional user information from the directory 745. In some aspects, theidentity provider gateway 725 may have (and/or have access to) adatabase with the additional user information. In these examples, theidentity provider gateway 725 might not transmit a request to thedirectory 745 for the user information, and may instead access theinformation from the database.

In step 1016, the identity provider gateway 725 may generate (e.g.,construct), using the user identifier and/or the additional userinformation from the directory 745, an authentication token, such as aSAML token. For example, the token may comprise a digitally signedassertion with the user's identifier, roots, and/or other data about theuser.

In step 1018, the identity provider gateway 725 may transmit, to theclient device (e.g., running the application 710), the authenticationtoken (e.g., SAML token) and/or a request to post the token to theservice provider 720. Step 1018 may be similar to step 856, which waspreviously described.

In step 1020, the client application 710 may transmit, to the serviceprovider 720, the request to post the token. The application 710 maypresent the token (e.g., SAML token) to the service provider 720 toobtain access to resources of the service provider 720. Step 1020 may besimilar to step 858, which was previously described.

In step 1022, the service provider 720 may process the token and grant,to the client device, access to resources. Step 1022 may be similar tostep 860, which was previously described.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice, from a user device, and via a secure channel between the userdevice and the computing device, an authentication request associatedwith a client certificate; determining whether the authenticationrequest was received via the secure channel; extracting, by thecomputing device, from the client certificate, and based on adetermination that the authentication request was received via thesecure channel, a device identifier for the user device; sending, by thecomputing device and to a server, data indicating the device identifierassociated with the user device; receiving, by the computing device andfrom the server, data indicating whether the user device is compliantwith one or more security policies; and determining, by the computingdevice and based on the data indicating whether the user device iscompliant with one or more security policies, whether to grant the userdevice access to a service.
 2. The method of claim 1, furthercomprising: detecting a request, by the user device, to access thecomputing device; intercepting, by a communication application, therequest to access the computing device; and establishing, by thecommunication application, the secure channel between the user deviceand the computing device.
 3. The method of claim 1, wherein the securechannel comprises a virtual private network (VPN) tunnel.
 4. The methodof claim 1, further comprising: establishing the secure channel betweenthe user device and the computing device in response to a request, froma service provider of the service, to redirect the authenticationrequest to the computing device.
 5. The method of claim 1, furthercomprising: after determining to grant access to the service,retrieving, by the computing device, cached authentication dataassociated with the user device; generating, by the computing device andusing the cached authentication data, an authentication token; andsending, by the computing device and to the user device, theauthentication token.
 6. The method of claim 5, wherein theauthentication token is configured to be used by the user device toaccess the service.
 7. The method of claim 1, further comprising:determining, by the computing device, that authentication dataassociated with the user device is not cached at the computing device;in response to determining that the authentication data is not cached atthe computing device, sending, by the computing device and to the userdevice, a request for the authentication data from an identity providerdevice; receiving, by the computing device, from the user device, andvia the identity provider device, the authentication data associatedwith the user device; and caching, by the computing device, theauthentication data associated with the user device.
 8. The method ofclaim 7, further comprising: retrieving, by the computing device, thecached authentication data associated with the user device; generating,by the computing device and using the cached authentication data, anauthentication token; and sending, by the computing device and to theuser device, the authentication token.
 9. The method of claim 7, furthercomprising: after a predetermined amount of time, removing, by thecomputing device, the cached authentication data associated with theuser device.
 10. The method of claim 1, further comprising: afterdetermining to grant access to the service, determining, by thecomputing device, and from information associated with theauthentication request, a user identifier associated with a user of theuser device; generating, by the computing device and using the useridentifier, an authentication token; and sending, by the computingdevice and to the user device, the authentication token.
 11. The methodof claim 10, further comprising: after determining the user identifier,sending, by the computing device and to a directory service, a requestfor additional data associated with the user of the user device; andreceiving, by the computing device and from the directory service, theadditional data associated with the user of the user device, whereingenerating the authentication token comprises generating theauthentication token using the user identifier and the additional dataassociated with the user received from the directory service.
 12. Anapparatus comprising: a processor; and memory storingcomputer-executable instructions that, when executed by the processor,cause the apparatus to: receive, from a user device and via a securechannel between the apparatus and the user device, an authenticationrequest associated with a client certificate; determine whether theauthentication request was received via the secure channel; extract,from the client certificate and based on a determination that theauthentication request was received via the secure channel, a deviceidentifier for the user device; send, to a server, data indicating thedevice identifier associated with the user device; receive, from theserver, data indicating whether the user device is compliant with one ormore security policies; and determine, based on the data indicatingwhether the user device is compliant with one or more security policies,whether to grant the user device access to a service.
 13. The apparatusof claim 12, wherein the memory stores computer-executable instructionsthat, when executed by the processor, cause the apparatus to: afterdetermining to grant access to the service, retrieve cachedauthentication data associated with the user device; generate, using thecached authentication data, an authentication token; and send, to theuser device, the authentication token.
 14. The apparatus of claim 13,wherein the authentication token is configured to be used by the userdevice to access the service.
 15. The apparatus of claim 12, wherein thememory stores computer-executable instructions that, when executed bythe processor, cause the apparatus to: determine that authenticationdata associated with the user device is not cached at the apparatus; inresponse to determining that the authentication data is not cached atthe apparatus, send, to the user device, a request for theauthentication data from an identity provider device; receive, from theuser device and via the identity provider device, the authenticationdata associated with the user device; and cache the authentication dataassociated with the user device.
 16. The apparatus of claim 15, whereinthe memory stores computer-executable instructions that, when executedby the processor, cause the apparatus to: retrieve the cachedauthentication data associated with the user device; generate, using thecached authentication data, an authentication token; and send, to theuser device, the authentication token.
 17. The apparatus of claim 12,wherein the memory stores computer-executable instructions that, whenexecuted by the processor, cause the apparatus to: after determining togrant access to the service, determine, from information associated withthe authentication request, a user identifier associated with a user ofthe user device; generate, using the user identifier, an authenticationtoken; and send, to the user device, the authentication token.
 18. Asystem comprising: a user device; and a computing device, wherein theuser device comprises: a processor; and memory storingcomputer-executable instructions that, when executed by the processor ofthe user device, cause the user device to: send, to the computing deviceand via a secure channel between the user device and the computingdevice, an authentication request associated with a client certificate,and wherein the computing device comprises: a processor; and memorystoring computer-executable instructions that, when executed by theprocessor of the computing device, cause the computing device to:determine whether the authentication request was received via the securechannel; extract, from the client certificate and based on adetermination that the authentication request was received via thesecure channel, a device identifier for the user device; send, to aserver, data indicating the device identifier associated with the userdevice; receive, from the server, data indicating whether the userdevice is compliant with one or more security policies; and determine,based on the data indicating whether the user device is compliant withone or more security policies, whether to grant the user device accessto a service.
 19. The system of claim 18, wherein the memory of the userdevice stores computer-executable instructions that, when executed bythe processor of the user device, cause the user device to: detect arequest to access the computing device; intercept, by a communicationapplication, the request to access the computing device; and establish,by the communication application, the secure channel between the userdevice and the computing device.
 20. The system of claim 18, wherein thememory of the user device stores computer-executable instructions that,when executed by the processor of the user device, cause the user deviceto: establish the secure channel between the user device and thecomputing device in response to a request, from a service provider ofthe service, to redirect the authentication request to the computingdevice.